Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae727abbd16c246ac292c8d05f895d0b301f7eba449d8ebcd8ceb0c04aee6e3

Tx prefix hash: 4545c982b8adfdcc1276c21848e9719221f5cbcc5fb81be46d3b3db219340420
Tx public key: 47aab11c29ca3c37143d85d3e4cef86287a020e2facaec1b3ada59e8f58cedda
Timestamp: 1703689940 Timestamp [UCT]: 2023-12-27 15:12:20 Age [y:d:h:m:s]: 01:177:16:45:03
Block: 922337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387972 RingCT/type: yes/0
Extra: 0147aab11c29ca3c37143d85d3e4cef86287a020e2facaec1b3ada59e8f58cedda02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6f487a09a377a3e5b0c01a00c8b07841db208e0ee43fc1ebd229ea786b4503a 0.600000000000 1380033 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": 922347, "vin": [ { "gen": { "height": 922337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6f487a09a377a3e5b0c01a00c8b07841db208e0ee43fc1ebd229ea786b4503a" } } ], "extra": [ 1, 71, 170, 177, 28, 41, 202, 60, 55, 20, 61, 133, 211, 228, 206, 248, 98, 135, 160, 32, 226, 250, 202, 236, 27, 58, 218, 89, 232, 245, 140, 237, 218, 2, 17, 0, 0, 0, 1, 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