Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb97c58cbcaac1df9b22db9ddf7d392106893cc5b7343664d1c8cd8dc438b127

Tx prefix hash: 4c362a3e22b988a1d89a59a20d75b5b3d8c5c837528b363feafcf11b656bb8ad
Tx public key: 6605b08d7be4934691b927051f542a62ebb10fef16ef3eaee65dc924b1e52ac1
Timestamp: 1728943969 Timestamp [UCT]: 2024-10-14 22:12:49 Age [y:d:h:m:s]: 01:025:07:10:32
Block: 1131708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276443 RingCT/type: yes/0
Extra: 016605b08d7be4934691b927051f542a62ebb10fef16ef3eaee65dc924b1e52ac1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b66c293c3164ee22ea6bad331a95485f2d72ac5912f3107f2fa8b45b6b3cd2 0.600000000000 1614613 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": 1131718, "vin": [ { "gen": { "height": 1131708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b66c293c3164ee22ea6bad331a95485f2d72ac5912f3107f2fa8b45b6b3cd2" } } ], "extra": [ 1, 102, 5, 176, 141, 123, 228, 147, 70, 145, 185, 39, 5, 31, 84, 42, 98, 235, 177, 15, 239, 22, 239, 62, 174, 230, 93, 201, 36, 177, 229, 42, 193, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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