Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3474a60414ac84a7a3b906d01557cd31912116aabd77b0161ade8a77897825ed

Tx prefix hash: 806f27e75fc7e4bb4498d9b94ddc2c5cc31f23b5bd284011bbb8d6b489f31a5f
Tx public key: 066981d49d8420c76839b24ef8cca714a8942f05a302c44e3e9b843e558b3c88
Timestamp: 1705478271 Timestamp [UCT]: 2024-01-17 07:57:51 Age [y:d:h:m:s]: 01:081:19:41:05
Block: 937145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319561 RingCT/type: yes/0
Extra: 01066981d49d8420c76839b24ef8cca714a8942f05a302c44e3e9b843e558b3c880211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96f4fb5e98ba1a0dc8e0d8f17d0109101b2f26df578ed768f8c01a145f1a5896 0.600000000000 1395189 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 937155, "vin": [ { "gen": { "height": 937145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96f4fb5e98ba1a0dc8e0d8f17d0109101b2f26df578ed768f8c01a145f1a5896" } } ], "extra": [ 1, 6, 105, 129, 212, 157, 132, 32, 199, 104, 57, 178, 78, 248, 204, 167, 20, 168, 148, 47, 5, 163, 2, 196, 78, 62, 155, 132, 62, 85, 139, 60, 136, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8