Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7d98acb85915a4390535eb203c62dd91987b7aa4b5094bd8f7698233e6e4398

Tx prefix hash: caf46297f21ad1fe2abbdf41beec1c1f6dc10b23c882439cf491fd8f1b241341
Tx public key: 2881d6a6c99b55f9547f8c0ed8c4961d87b1f23661f1ef3144e446226634c4bd
Timestamp: 1712153071 Timestamp [UCT]: 2024-04-03 14:04:31 Age [y:d:h:m:s]: 00:266:19:48:45
Block: 992473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191037 RingCT/type: yes/0
Extra: 012881d6a6c99b55f9547f8c0ed8c4961d87b1f23661f1ef3144e446226634c4bd0211000000053f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fbdbfcdc3563492f617180e8111a452ba51610c1446d28d9a9155c9fab1fe21 0.600000000000 1452815 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": 992483, "vin": [ { "gen": { "height": 992473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fbdbfcdc3563492f617180e8111a452ba51610c1446d28d9a9155c9fab1fe21" } } ], "extra": [ 1, 40, 129, 214, 166, 201, 155, 85, 249, 84, 127, 140, 14, 216, 196, 150, 29, 135, 177, 242, 54, 97, 241, 239, 49, 68, 228, 70, 34, 102, 52, 196, 189, 2, 17, 0, 0, 0, 5, 63, 130, 249, 251, 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