Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d0c789024f86d5b1a841c3d320579d655a67ebbadf368b053f442d31bd5a30

Tx prefix hash: 897457de7f098b5275b89c79fae580c4faed08e47e5fb782c718ed45030dd568
Tx public key: ec78f6afe0ce1deb2ca6a37ccf16b7e56cb3e0c5b7a74d0b2e40191ab8dc2df1
Timestamp: 1718746854 Timestamp [UCT]: 2024-06-18 21:40:54 Age [y:d:h:m:s]: 00:282:08:36:33
Block: 1047171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201763 RingCT/type: yes/0
Extra: 01ec78f6afe0ce1deb2ca6a37ccf16b7e56cb3e0c5b7a74d0b2e40191ab8dc2df102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b4c6307e5233a54d6975b88fc9e6cf511576fc96ba701599f94dc8465a2da28 0.600000000000 1516990 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": 1047181, "vin": [ { "gen": { "height": 1047171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b4c6307e5233a54d6975b88fc9e6cf511576fc96ba701599f94dc8465a2da28" } } ], "extra": [ 1, 236, 120, 246, 175, 224, 206, 29, 235, 44, 166, 163, 124, 207, 22, 183, 229, 108, 179, 224, 197, 183, 167, 77, 11, 46, 64, 25, 26, 184, 220, 45, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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