Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64dd43d946484b58632193dc80df90d57639e46192cacb9c0f3a7d3cc23d8a39

Tx prefix hash: 3fce241f19f3909b3c98a7a74402c92b7d3beae75bf9c0f2c58c4b692dc0c539
Tx public key: ca9ce31f9588125a936f1c06a46cd8a5d8437ffd75435eeab3b2a88adc07c8d8
Timestamp: 1736020701 Timestamp [UCT]: 2025-01-04 19:58:21 Age [y:d:h:m:s]: 00:318:16:19:07
Block: 1190244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225271 RingCT/type: yes/0
Extra: 01ca9ce31f9588125a936f1c06a46cd8a5d8437ffd75435eeab3b2a88adc07c8d802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9b1fa1e6449a8dde4a819fc3a21ce04100f9770e17aa7e3db8eb63de0b4e36e 0.600000000000 1676759 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": 1190254, "vin": [ { "gen": { "height": 1190244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9b1fa1e6449a8dde4a819fc3a21ce04100f9770e17aa7e3db8eb63de0b4e36e" } } ], "extra": [ 1, 202, 156, 227, 31, 149, 136, 18, 90, 147, 111, 28, 6, 164, 108, 216, 165, 216, 67, 127, 253, 117, 67, 94, 234, 179, 178, 168, 138, 220, 7, 200, 216, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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