Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f6dd4e52e5a68b2b88310a1e497526b92112456e0c3f854c9d0299c2d57d4f

Tx prefix hash: 41eaf4b093eb18df3685bbde3004bd742f3c44cc44faaf51d1a186c665b6e55d
Tx public key: d978322b90e8bf6a02239b8584b43845312d9b2f8d1b9bce84d02a2e9ddbfcf3
Timestamp: 1659225037 Timestamp [UCT]: 2022-07-30 23:50:37 Age [y:d:h:m:s]: 02:249:13:40:31
Block: 555309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699557 RingCT/type: yes/0
Extra: 01d978322b90e8bf6a02239b8584b43845312d9b2f8d1b9bce84d02a2e9ddbfcf30211000000016570b1ef000000000000000000

1 output(s) for total of 8.872191103000 dcy

stealth address amount amount idx
00: bfca1f7810edff107d422c7a50d8d33e99794d1d16f5fb6f19fc3d7f15302d01 8.872191103000 987203 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": 555319, "vin": [ { "gen": { "height": 555309 } } ], "vout": [ { "amount": 8872191103, "target": { "key": "bfca1f7810edff107d422c7a50d8d33e99794d1d16f5fb6f19fc3d7f15302d01" } } ], "extra": [ 1, 217, 120, 50, 43, 144, 232, 191, 106, 2, 35, 155, 133, 132, 180, 56, 69, 49, 45, 155, 47, 141, 27, 155, 206, 132, 208, 42, 46, 157, 219, 252, 243, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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