Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da48babbe93390d879b47bb82e097f7d5ae58b0ecc7e8759fef34bcdf0ed04c

Tx prefix hash: 505f2b9891292fe574c0d0815ab7ce16e2c5a88bb191eba3491377ead70554a8
Tx public key: 378e04d6d3bf8f316d408bed5faf3c6de8a78ec2e89c476e47babf4657066748
Timestamp: 1694322045 Timestamp [UCT]: 2023-09-10 05:00:45 Age [y:d:h:m:s]: 01:220:23:35:36
Block: 844856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419046 RingCT/type: yes/0
Extra: 01378e04d6d3bf8f316d408bed5faf3c6de8a78ec2e89c476e47babf465706674802110000000c4b8f5122000000000000000000

1 output(s) for total of 0.974184959000 dcy

stealth address amount amount idx
00: 6742db07269bb066397dc514d8e9947065d723d56ccbf4d7d98caa6991d6ef1e 0.974184959000 1298192 of 0

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": 844866, "vin": [ { "gen": { "height": 844856 } } ], "vout": [ { "amount": 974184959, "target": { "key": "6742db07269bb066397dc514d8e9947065d723d56ccbf4d7d98caa6991d6ef1e" } } ], "extra": [ 1, 55, 142, 4, 214, 211, 191, 143, 49, 109, 64, 139, 237, 95, 175, 60, 109, 232, 167, 142, 194, 232, 156, 71, 110, 71, 186, 191, 70, 87, 6, 103, 72, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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