Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82fa9c9e7d50ea46f19924609ebd4167049dc1bb4c48c96ec6aaf7732dfdd5e

Tx prefix hash: 4ec2dc6f2a4b33bb804164c4b8b38041abb0861617f27e46278013eace900ec8
Tx public key: 9b99adc546d2de7743162d8c6c0384adf98a18a933f3f1ce70ef4bfb0cf1dd73
Timestamp: 1731455090 Timestamp [UCT]: 2024-11-12 23:44:50 Age [y:d:h:m:s]: 00:219:01:42:25
Block: 1152421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156309 RingCT/type: yes/0
Extra: 019b99adc546d2de7743162d8c6c0384adf98a18a933f3f1ce70ef4bfb0cf1dd730211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 436fece9977cbabdaf74b16c5506601d04c2e578e9c57dd23654067453d46d22 0.600000000000 1638018 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": 1152431, "vin": [ { "gen": { "height": 1152421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "436fece9977cbabdaf74b16c5506601d04c2e578e9c57dd23654067453d46d22" } } ], "extra": [ 1, 155, 153, 173, 197, 70, 210, 222, 119, 67, 22, 45, 140, 108, 3, 132, 173, 249, 138, 24, 169, 51, 243, 241, 206, 112, 239, 75, 251, 12, 241, 221, 115, 2, 17, 0, 0, 0, 3, 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