Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a312d5eb9f0da3be6d1cdfa517ea000ff7b100a86e9ec0679cbbd9451d884126

Tx prefix hash: 58e001ddc7a42bd0ec995b728114692f6bb63a3f8d35154358ab85f7060f51e0
Tx public key: 32e9fea1e428429d9065e40834e3d3ae401377d6d0a8bce7e7b5be80fc65bdb4
Timestamp: 1717271806 Timestamp [UCT]: 2024-06-01 19:56:46 Age [y:d:h:m:s]: 00:312:07:33:22
Block: 1034947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223202 RingCT/type: yes/0
Extra: 0132e9fea1e428429d9065e40834e3d3ae401377d6d0a8bce7e7b5be80fc65bdb40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3541d51e3609cf09ea2021f16350e6445f6c9256ba9d3c2440365f839515b34c 0.600000000000 1503466 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": 1034957, "vin": [ { "gen": { "height": 1034947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3541d51e3609cf09ea2021f16350e6445f6c9256ba9d3c2440365f839515b34c" } } ], "extra": [ 1, 50, 233, 254, 161, 228, 40, 66, 157, 144, 101, 228, 8, 52, 227, 211, 174, 64, 19, 119, 214, 208, 168, 188, 231, 231, 181, 190, 128, 252, 101, 189, 180, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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