Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8bb32c84eeecdda2e73df4f147bedcfd51d54bd4006a7457658e665427fcfe7

Tx prefix hash: dd68847dc681e51c3c1a9560d4f4c42e17f7f3508bbd2c9bae69ec583bbccd48
Tx public key: 9372ba0cf0534988fbf4c36c0e40c6ab6de7703588989aace812b89c033b73d2
Timestamp: 1702018597 Timestamp [UCT]: 2023-12-08 06:56:37 Age [y:d:h:m:s]: 01:123:07:44:53
Block: 908486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349280 RingCT/type: yes/0
Extra: 019372ba0cf0534988fbf4c36c0e40c6ab6de7703588989aace812b89c033b73d202110000000be6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b35d8d2cba8ebc4b8ca2c62bc0d81add193e4a3706ac0ff65e8e9000e195a62 0.600000000000 1365519 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": 908496, "vin": [ { "gen": { "height": 908486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b35d8d2cba8ebc4b8ca2c62bc0d81add193e4a3706ac0ff65e8e9000e195a62" } } ], "extra": [ 1, 147, 114, 186, 12, 240, 83, 73, 136, 251, 244, 195, 108, 14, 64, 198, 171, 109, 231, 112, 53, 136, 152, 154, 172, 232, 18, 184, 156, 3, 59, 115, 210, 2, 17, 0, 0, 0, 11, 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