Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc94302cdf59a474785b9d5518ae5b9f8d3ee65e717ac5bd8e55428e36a79eea

Tx prefix hash: fb8dc847aedf7a859189f95491ada4758373b41a486f06049ca9b6a9b012abd6
Tx public key: 809e4e602d3a150fc82af3811b304f0220105693ca4e7775f09b97508a9a9f40
Timestamp: 1737044535 Timestamp [UCT]: 2025-01-16 16:22:15 Age [y:d:h:m:s]: 00:152:08:28:01
Block: 1198712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108590 RingCT/type: yes/0
Extra: 01809e4e602d3a150fc82af3811b304f0220105693ca4e7775f09b97508a9a9f400211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57c29627ea62cd1e84d121d33fa7cd791789ba1ab52d57e5f8b0f00ded2ba523 0.600000000000 1685339 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": 1198722, "vin": [ { "gen": { "height": 1198712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57c29627ea62cd1e84d121d33fa7cd791789ba1ab52d57e5f8b0f00ded2ba523" } } ], "extra": [ 1, 128, 158, 78, 96, 45, 58, 21, 15, 200, 42, 243, 129, 27, 48, 79, 2, 32, 16, 86, 147, 202, 78, 119, 117, 240, 155, 151, 80, 138, 154, 159, 64, 2, 17, 0, 0, 0, 5, 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