Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beafd79f0df62ae065c343a3d12929bb7ac10f1771467463a94d667d81ebf18b

Tx prefix hash: 1b30996e72f8ae6ac6008854ea8077a9a2a9cbd2e4a2919a4253b60e7af9402a
Tx public key: ab2dee03f80d7eaa0f984628716b80419bfacccf0b7ef4ec86810006a4def8d2
Timestamp: 1674862287 Timestamp [UCT]: 2023-01-27 23:31:27 Age [y:d:h:m:s]: 02:071:14:12:38
Block: 684230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572786 RingCT/type: yes/0
Extra: 01ab2dee03f80d7eaa0f984628716b80419bfacccf0b7ef4ec86810006a4def8d20211000000055029cbac000000000000000000

1 output(s) for total of 3.317889431000 dcy

stealth address amount amount idx
00: ae41bb22736c0163442c9c416b888e71aad3829c6d91294ee567eb5b68df0202 3.317889431000 1126445 of 0

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": 684240, "vin": [ { "gen": { "height": 684230 } } ], "vout": [ { "amount": 3317889431, "target": { "key": "ae41bb22736c0163442c9c416b888e71aad3829c6d91294ee567eb5b68df0202" } } ], "extra": [ 1, 171, 45, 238, 3, 248, 13, 126, 170, 15, 152, 70, 40, 113, 107, 128, 65, 155, 250, 204, 207, 11, 126, 244, 236, 134, 129, 0, 6, 164, 222, 248, 210, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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