Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e3e246ef19a880b0711d49da866b8af3e76c334dc446341ff52d2eb56b0422

Tx prefix hash: 890224e9480e193c3692d723f80c620b0b38ecfffb10e7f284e7bc7678b09cbc
Tx public key: 1932fe0201251ee4e30aa61ff8b3eaa9a9306292a1c066fe2ab2dfed1edb160e
Timestamp: 1726915793 Timestamp [UCT]: 2024-09-21 10:49:53 Age [y:d:h:m:s]: 00:202:15:25:03
Block: 1114892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144655 RingCT/type: yes/0
Extra: 011932fe0201251ee4e30aa61ff8b3eaa9a9306292a1c066fe2ab2dfed1edb160e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e131c713f7393cf361422167d2c4496ce2cccd245e17ce4d25b48c33f52840c4 0.600000000000 1594831 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": 1114902, "vin": [ { "gen": { "height": 1114892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e131c713f7393cf361422167d2c4496ce2cccd245e17ce4d25b48c33f52840c4" } } ], "extra": [ 1, 25, 50, 254, 2, 1, 37, 30, 228, 227, 10, 166, 31, 248, 179, 234, 169, 169, 48, 98, 146, 161, 192, 102, 254, 42, 178, 223, 237, 30, 219, 22, 14, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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