Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a0fab23104145e0f9bd351cecbea3b7c8b4faf3ed29b7440279e2c3399473c

Tx prefix hash: aadff62bfd43ab2cc3620fb35f4c0f3d191011ac3dc5a7faf1e8660d07c930fe
Tx public key: 4399746ba354bb1c6c8a1ecdc32d390bc74886474cdd21bcf2845cf66dc86e31
Timestamp: 1704203886 Timestamp [UCT]: 2024-01-02 13:58:06 Age [y:d:h:m:s]: 01:129:07:48:28
Block: 926589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353559 RingCT/type: yes/0
Extra: 014399746ba354bb1c6c8a1ecdc32d390bc74886474cdd21bcf2845cf66dc86e3102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bc9c82102e7e99c5d7a4ce3b3869756f5a82e6111a7940bf6e3cf8f79a856b4 0.600000000000 1384383 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": 926599, "vin": [ { "gen": { "height": 926589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bc9c82102e7e99c5d7a4ce3b3869756f5a82e6111a7940bf6e3cf8f79a856b4" } } ], "extra": [ 1, 67, 153, 116, 107, 163, 84, 187, 28, 108, 138, 30, 205, 195, 45, 57, 11, 199, 72, 134, 71, 76, 221, 33, 188, 242, 132, 92, 246, 109, 200, 110, 49, 2, 17, 0, 0, 0, 3, 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