Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c28d5563e6fe34179a0b0626d37c07212e676c99cd74cd472d86cd554df229

Tx prefix hash: cb73804a50bb94e6c8fab3df2d1fed9d1d6e2af5c5f451f98dbc4d326db2e3b4
Tx public key: 4f94e389d23e63d1ba5d5f628877633532258e38bb83e68ea57e1f2aad310a73
Timestamp: 1751003106 Timestamp [UCT]: 2025-06-27 05:45:06 Age [y:d:h:m:s]: 00:142:04:57:27
Block: 1313674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99648 RingCT/type: yes/0
Extra: 014f94e389d23e63d1ba5d5f628877633532258e38bb83e68ea57e1f2aad310a7302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d241f6d9c7e0e763d9b9ae72f090b8e398201ef6238826d01f42a1493676570 0.600000000000 1801315 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": 1313684, "vin": [ { "gen": { "height": 1313674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d241f6d9c7e0e763d9b9ae72f090b8e398201ef6238826d01f42a1493676570" } } ], "extra": [ 1, 79, 148, 227, 137, 210, 62, 99, 209, 186, 93, 95, 98, 136, 119, 99, 53, 50, 37, 142, 56, 187, 131, 230, 142, 165, 126, 31, 42, 173, 49, 10, 115, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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