Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909c77953e72a39521b9e294a584e929f6001e7a31df6471291125a411ee78eb

Tx prefix hash: b44437063a36eca423dde45a1e081d8334703daf7d88263b5ba93a3464a75411
Tx public key: d3827dfdf13abd38a0f61b5c11f357233c0ff2542bf254d22d31fe67a226ef0a
Timestamp: 1694623722 Timestamp [UCT]: 2023-09-13 16:48:42 Age [y:d:h:m:s]: 01:073:00:51:54
Block: 847363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313474 RingCT/type: yes/0
Extra: 01d3827dfdf13abd38a0f61b5c11f357233c0ff2542bf254d22d31fe67a226ef0a021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.955728824000 dcy

stealth address amount amount idx
00: 790204e0b63483fc75a9fdf8ce86738bd3ede8267eb0744d0db9fee38f99454a 0.955728824000 1300881 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": 847373, "vin": [ { "gen": { "height": 847363 } } ], "vout": [ { "amount": 955728824, "target": { "key": "790204e0b63483fc75a9fdf8ce86738bd3ede8267eb0744d0db9fee38f99454a" } } ], "extra": [ 1, 211, 130, 125, 253, 241, 58, 189, 56, 160, 246, 27, 92, 17, 243, 87, 35, 60, 15, 242, 84, 43, 242, 84, 210, 45, 49, 254, 103, 162, 38, 239, 10, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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