Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03e5039652d61c60433c8862ca0d7c3287c1461ac093654a767dece5b5b78811

Tx prefix hash: abb8f83c8b0cbe9e2da90ceb79c018d177aa83a1e08c1c456785578b0ecc8f8a
Tx public key: 73d254f96d79622b2b1df3f66132700574c5fc4abe307ca1aef93e99e2a46d02
Timestamp: 1737808204 Timestamp [UCT]: 2025-01-25 12:30:04 Age [y:d:h:m:s]: 00:143:05:50:23
Block: 1205003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102111 RingCT/type: yes/0
Extra: 0173d254f96d79622b2b1df3f66132700574c5fc4abe307ca1aef93e99e2a46d02021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b146699ef9326dc4baf82ffd1448dc13a85b84d3c62c41ec192f16c87cc5aac5 0.600000000000 1691698 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": 1205013, "vin": [ { "gen": { "height": 1205003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b146699ef9326dc4baf82ffd1448dc13a85b84d3c62c41ec192f16c87cc5aac5" } } ], "extra": [ 1, 115, 210, 84, 249, 109, 121, 98, 43, 43, 29, 243, 246, 97, 50, 112, 5, 116, 197, 252, 74, 190, 48, 124, 161, 174, 249, 62, 153, 226, 164, 109, 2, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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