Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3975a75957521bb2056e477d6ba9bb948dcd3430b540e3bfd6849ad81eec6bf

Tx prefix hash: 13e824a1d33fed3877b42d52f25b663be77ea8591d5ac5f846c5697ee9fef678
Tx public key: 669cd0e197395a02df031e5e122a49423aa289fc01cbe7f0fc1cc18a79f7715c
Timestamp: 1699379119 Timestamp [UCT]: 2023-11-07 17:45:19 Age [y:d:h:m:s]: 01:139:05:45:48
Block: 886605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360683 RingCT/type: yes/0
Extra: 01669cd0e197395a02df031e5e122a49423aa289fc01cbe7f0fc1cc18a79f7715c021100000004679a8a81000000000000000000

1 output(s) for total of 0.708450630000 dcy

stealth address amount amount idx
00: 781390ff157b1e043da1272c019cb639e83b3d8b790c8ed1246654b7f726dbf7 0.708450630000 1342432 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": 886615, "vin": [ { "gen": { "height": 886605 } } ], "vout": [ { "amount": 708450630, "target": { "key": "781390ff157b1e043da1272c019cb639e83b3d8b790c8ed1246654b7f726dbf7" } } ], "extra": [ 1, 102, 156, 208, 225, 151, 57, 90, 2, 223, 3, 30, 94, 18, 42, 73, 66, 58, 162, 137, 252, 1, 203, 231, 240, 252, 28, 193, 138, 121, 247, 113, 92, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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