Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afb65d6af97b308c5bb95d29593fa2650b7c77276561a53b583be7a280396ce7

Tx prefix hash: dfd50ac432f28704cb5c6d63ad21054b55ffdb5205935fa61d31c8427955a5d5
Tx public key: 202c6e4006bb51a6123185173d5c906a3a7702ef16b07a68f6d27cf4ccb7ddf5
Timestamp: 1745915369 Timestamp [UCT]: 2025-04-29 08:29:29 Age [y:d:h:m:s]: 00:007:12:26:40
Block: 1271904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5361 RingCT/type: yes/0
Extra: 01202c6e4006bb51a6123185173d5c906a3a7702ef16b07a68f6d27cf4ccb7ddf50211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7035f8c027b4f613fdc5ed131ff214a3b2730829f0c3360be76e9fd249ec76b4 0.600000000000 1759175 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": 1271914, "vin": [ { "gen": { "height": 1271904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7035f8c027b4f613fdc5ed131ff214a3b2730829f0c3360be76e9fd249ec76b4" } } ], "extra": [ 1, 32, 44, 110, 64, 6, 187, 81, 166, 18, 49, 133, 23, 61, 92, 144, 106, 58, 119, 2, 239, 22, 176, 122, 104, 246, 210, 124, 244, 204, 183, 221, 245, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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