Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e18f7dfc342df5359e0dcda470da007cd092d4f74f5e7fdbf6fa8013550444

Tx prefix hash: 78aeda27f2e5df8869f1a955ae7cd670c6348869377cb0daa71c5a341928c769
Tx public key: f64a09d5b67c74beac94585f2ccc9a1b59810981d3eca7bf5188bfc425c6f68d
Timestamp: 1711503974 Timestamp [UCT]: 2024-03-27 01:46:14 Age [y:d:h:m:s]: 00:232:08:20:04
Block: 987143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166314 RingCT/type: yes/0
Extra: 01f64a09d5b67c74beac94585f2ccc9a1b59810981d3eca7bf5188bfc425c6f68d02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa38308a9fa5f05e848807664e0010b7a0124436339782a299122777095d38b0 0.600000000000 1447384 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": 987153, "vin": [ { "gen": { "height": 987143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa38308a9fa5f05e848807664e0010b7a0124436339782a299122777095d38b0" } } ], "extra": [ 1, 246, 74, 9, 213, 182, 124, 116, 190, 172, 148, 88, 95, 44, 204, 154, 27, 89, 129, 9, 129, 211, 236, 167, 191, 81, 136, 191, 196, 37, 198, 246, 141, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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