Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b343a79fc4f5e1d998a299f9e646e82542973427edcae3b4115e4a8f72a95191

Tx prefix hash: f4d8c6ba43bc2992196bb134398ed406f4f22c6e73e35649efeaa48c8f6c1657
Tx public key: f5b315aafdc701ddf4a550712c31abddfb88eec5dcf188d2ed2526fbdb354a19
Timestamp: 1695479870 Timestamp [UCT]: 2023-09-23 14:37:50 Age [y:d:h:m:s]: 01:154:08:25:29
Block: 854472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371345 RingCT/type: yes/0
Extra: 01f5b315aafdc701ddf4a550712c31abddfb88eec5dcf188d2ed2526fbdb354a19021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.905273080000 dcy

stealth address amount amount idx
00: efae064fc931d62f31e0a4b500f9a1eb9ee15e7df96f7677b0ae6f0e6adbb30b 0.905273080000 1308446 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": 854482, "vin": [ { "gen": { "height": 854472 } } ], "vout": [ { "amount": 905273080, "target": { "key": "efae064fc931d62f31e0a4b500f9a1eb9ee15e7df96f7677b0ae6f0e6adbb30b" } } ], "extra": [ 1, 245, 179, 21, 170, 253, 199, 1, 221, 244, 165, 80, 113, 44, 49, 171, 221, 251, 136, 238, 197, 220, 241, 136, 210, 237, 37, 38, 251, 219, 53, 74, 25, 2, 17, 0, 0, 0, 4, 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