Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1955a58d7210b5f004bfa1af75e81294821bd1287959361715b6e05ebf17977f

Tx prefix hash: 97c81267669ad8d932a3dc79b389b84d6a66fe9f133b7cba42b1b0113d88e9bd
Tx public key: d95929d59d3c8f6218724f091ff33fcb5a831e4d013e97ef1b01402eb79324af
Timestamp: 1746624656 Timestamp [UCT]: 2025-05-07 13:30:56 Age [y:d:h:m:s]: 00:187:11:12:54
Block: 1277764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131682 RingCT/type: yes/0
Extra: 01d95929d59d3c8f6218724f091ff33fcb5a831e4d013e97ef1b01402eb79324af02110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde9aed5bafdd801dbf9115df004cef39092747ea43ef153cd073e83a58246b0 0.600000000000 1765121 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": 1277774, "vin": [ { "gen": { "height": 1277764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde9aed5bafdd801dbf9115df004cef39092747ea43ef153cd073e83a58246b0" } } ], "extra": [ 1, 217, 89, 41, 213, 157, 60, 143, 98, 24, 114, 79, 9, 31, 243, 63, 203, 90, 131, 30, 77, 1, 62, 151, 239, 27, 1, 64, 46, 183, 147, 36, 175, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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