Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa874af71d67394178c2d9181e79182746e253d6be2b46e9fec00d6183140781

Tx prefix hash: e3367d4a5682ea0a692c725ef5b9c10622b0f4f388b74c7a6be08d4d53e5d314
Tx public key: 77427dae16a6d295835b0b3a21e5fbcb0f214cf75e2aba4b72e664d348af19c4
Timestamp: 1727287524 Timestamp [UCT]: 2024-09-25 18:05:24 Age [y:d:h:m:s]: 00:194:19:40:17
Block: 1117974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139042 RingCT/type: yes/0
Extra: 0177427dae16a6d295835b0b3a21e5fbcb0f214cf75e2aba4b72e664d348af19c402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fa4497e4f458c130cc873213ce2311a4b1f1a45502e9e509c86493b01512fdf 0.600000000000 1599007 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": 1117984, "vin": [ { "gen": { "height": 1117974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fa4497e4f458c130cc873213ce2311a4b1f1a45502e9e509c86493b01512fdf" } } ], "extra": [ 1, 119, 66, 125, 174, 22, 166, 210, 149, 131, 91, 11, 58, 33, 229, 251, 203, 15, 33, 76, 247, 94, 42, 186, 75, 114, 230, 100, 211, 72, 175, 25, 196, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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