Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8382269c0c2b0bcc82d4b86b05d935e29a2c8d9783a4020324ffd1c4c2cb21a6

Tx prefix hash: 81f1fa65b16cbe913324724d98936fedc642aca6c48e84c3fc6d8acab4e2c6e3
Tx public key: c716366c0b0ac4e1ff739db11a86e24f74e90f88ae8bed4adc3808e716508233
Timestamp: 1732897866 Timestamp [UCT]: 2024-11-29 16:31:06 Age [y:d:h:m:s]: 00:140:06:58:30
Block: 1164393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100084 RingCT/type: yes/0
Extra: 01c716366c0b0ac4e1ff739db11a86e24f74e90f88ae8bed4adc3808e7165082330211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93f50e7741d0e253b237d8ccc6b477ed3306ec7aeb5f50d873aa2f8cef172e4a 0.600000000000 1650066 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": 1164403, "vin": [ { "gen": { "height": 1164393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93f50e7741d0e253b237d8ccc6b477ed3306ec7aeb5f50d873aa2f8cef172e4a" } } ], "extra": [ 1, 199, 22, 54, 108, 11, 10, 196, 225, 255, 115, 157, 177, 26, 134, 226, 79, 116, 233, 15, 136, 174, 139, 237, 74, 220, 56, 8, 231, 22, 80, 130, 51, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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