Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5794839099436c4bd5e2d2ee17553db69f769774de77d10d3b91804ee50d95e7

Tx prefix hash: 1227333c284ac1febb6c13af2efe2da05820fffd272abe413257abee50d1e129
Tx public key: e3b8a2a5c069dbd196351062c39c975a02c2f663d2b6ee1ea4c640e1292f97d1
Timestamp: 1720875800 Timestamp [UCT]: 2024-07-13 13:03:20 Age [y:d:h:m:s]: 00:264:05:39:38
Block: 1064828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188758 RingCT/type: yes/0
Extra: 01e3b8a2a5c069dbd196351062c39c975a02c2f663d2b6ee1ea4c640e1292f97d102110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bd3056ac2544d51aec2d47871984353783d99bd2ff4db505ba72a140238d883 0.600000000000 1535367 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": 1064838, "vin": [ { "gen": { "height": 1064828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd3056ac2544d51aec2d47871984353783d99bd2ff4db505ba72a140238d883" } } ], "extra": [ 1, 227, 184, 162, 165, 192, 105, 219, 209, 150, 53, 16, 98, 195, 156, 151, 90, 2, 194, 246, 99, 210, 182, 238, 30, 164, 198, 64, 225, 41, 47, 151, 209, 2, 17, 0, 0, 0, 10, 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