Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd02e34a041daa6f604c09c0143cc418c828fdc7a3d6efbde77c05330ca55544

Tx prefix hash: 3262bc567d7cf28801bf5d642d6528c60393421cef42d304b85a224afc8db795
Tx public key: ec6fb334032daf78d80a189e8c71bd04ad3f20b1b9cbd5859d5f7a7c657ed26c
Timestamp: 1704995732 Timestamp [UCT]: 2024-01-11 17:55:32 Age [y:d:h:m:s]: 01:000:12:18:47
Block: 933145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261702 RingCT/type: yes/0
Extra: 01ec6fb334032daf78d80a189e8c71bd04ad3f20b1b9cbd5859d5f7a7c657ed26c02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1409bc5420f2cb420da3254e0356d7fece39e9da86f33c31ad82cbede016eb8 0.600000000000 1391101 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": 933155, "vin": [ { "gen": { "height": 933145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1409bc5420f2cb420da3254e0356d7fece39e9da86f33c31ad82cbede016eb8" } } ], "extra": [ 1, 236, 111, 179, 52, 3, 45, 175, 120, 216, 10, 24, 158, 140, 113, 189, 4, 173, 63, 32, 177, 185, 203, 213, 133, 157, 95, 122, 124, 101, 126, 210, 108, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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