Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3721689dde360ae847a3ccf29db3d52d933532a7a3a27098738c54fae955363e

Tx prefix hash: b50002a0700928d3c2166534519943c8a8e60f29b9f37314b72abc86dca88cdc
Tx public key: bfcee3891b9f0ed0de8824d17fee060dc1142199d3c40a61d1005624d2bca43e
Timestamp: 1683738085 Timestamp [UCT]: 2023-05-10 17:01:25 Age [y:d:h:m:s]: 01:349:13:43:45
Block: 757178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511081 RingCT/type: yes/0
Extra: 01bfcee3891b9f0ed0de8824d17fee060dc1142199d3c40a61d1005624d2bca43e02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.901757594000 dcy

stealth address amount amount idx
00: 154e3527ab5f191d608dd3e7a33073493e0858f4e9b806bbc3c535d6f2f5cbea 1.901757594000 1205605 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": 757188, "vin": [ { "gen": { "height": 757178 } } ], "vout": [ { "amount": 1901757594, "target": { "key": "154e3527ab5f191d608dd3e7a33073493e0858f4e9b806bbc3c535d6f2f5cbea" } } ], "extra": [ 1, 191, 206, 227, 137, 27, 159, 14, 208, 222, 136, 36, 209, 127, 238, 6, 13, 193, 20, 33, 153, 211, 196, 10, 97, 209, 0, 86, 36, 210, 188, 164, 62, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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