Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc29da0593914115b51203da024b27026a87df932da93e6d2baf96668b7e9c1f

Tx prefix hash: 31c6cf6e9d4b5a7e56409679715408ed6d819bd78bf4702bddeb17eae52cdb85
Tx public key: c3719a48398f1f1a0d1915fbeb2911194d65209be292821b8e65b88581f6ee10
Timestamp: 1715371719 Timestamp [UCT]: 2024-05-10 20:08:39 Age [y:d:h:m:s]: 01:186:22:17:31
Block: 1019206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392200 RingCT/type: yes/0
Extra: 01c3719a48398f1f1a0d1915fbeb2911194d65209be292821b8e65b88581f6ee1002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cf8fb7f35f4ac1816454f71ab44288ea0740d4fe60c4cffd47acd3a4e580d28 0.600000000000 1483111 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": 1019216, "vin": [ { "gen": { "height": 1019206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf8fb7f35f4ac1816454f71ab44288ea0740d4fe60c4cffd47acd3a4e580d28" } } ], "extra": [ 1, 195, 113, 154, 72, 57, 143, 31, 26, 13, 25, 21, 251, 235, 41, 17, 25, 77, 101, 32, 155, 226, 146, 130, 27, 142, 101, 184, 133, 129, 246, 238, 16, 2, 17, 0, 0, 0, 7, 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