Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e1f020c365946ddfc6c4a37add6ac18967edc0dfbfaea3ed798140c3c79748

Tx prefix hash: ff5b20bb648cadb93260aead938c6977db837b324f558460fc4960bcc85cb928
Tx public key: 786eb43cc726e4cea39102a08db284f5f75f8cb02fcc4c8c3ee0b4835605978c
Timestamp: 1702074835 Timestamp [UCT]: 2023-12-08 22:33:55 Age [y:d:h:m:s]: 01:038:06:40:10
Block: 908940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288721 RingCT/type: yes/0
Extra: 01786eb43cc726e4cea39102a08db284f5f75f8cb02fcc4c8c3ee0b4835605978c021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ec6b6edb59ca5d976b11dce0278ae9496b6c4014e6bbe4351a555e24e2b27a7 0.600000000000 1366003 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": 908950, "vin": [ { "gen": { "height": 908940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ec6b6edb59ca5d976b11dce0278ae9496b6c4014e6bbe4351a555e24e2b27a7" } } ], "extra": [ 1, 120, 110, 180, 60, 199, 38, 228, 206, 163, 145, 2, 160, 141, 178, 132, 245, 247, 95, 140, 176, 47, 204, 76, 140, 62, 224, 180, 131, 86, 5, 151, 140, 2, 17, 0, 0, 0, 6, 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