Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a26daf660a394497bd8dcccfeae06601e8b0e495a310f06e83b8b852af5c7af

Tx prefix hash: 86471d996199c52d91282e3afa50f508e220a4ecbac29da5de71f179a801c501
Tx public key: 246bd6f7ad49fb354ff41c5122f5348ce85dd9c5d8d3f9458db60b54387646bc
Timestamp: 1694550155 Timestamp [UCT]: 2023-09-12 20:22:35 Age [y:d:h:m:s]: 01:074:17:14:02
Block: 846743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314695 RingCT/type: yes/0
Extra: 01246bd6f7ad49fb354ff41c5122f5348ce85dd9c5d8d3f9458db60b54387646bc02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.960260363000 dcy

stealth address amount amount idx
00: 551a033a107943d0f9c51b358ac70a6361229f232f31d7faf96c4789258e5074 0.960260363000 1300223 of 0

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": 846753, "vin": [ { "gen": { "height": 846743 } } ], "vout": [ { "amount": 960260363, "target": { "key": "551a033a107943d0f9c51b358ac70a6361229f232f31d7faf96c4789258e5074" } } ], "extra": [ 1, 36, 107, 214, 247, 173, 73, 251, 53, 79, 244, 28, 81, 34, 245, 52, 140, 232, 93, 217, 197, 216, 211, 249, 69, 141, 182, 11, 84, 56, 118, 70, 188, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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