Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e8f2300544000bc0d6a4305e3d47db6d80635bb0f483e6e069eb325573e2646

Tx prefix hash: 98ee43f1db4b33da06ae3f2efd2df6707563f23cb6f1d95fcd7d6ff61282fa24
Tx public key: 11bb8d176cd38d743946e901ea40928711136b70e8db6bca5c149f7264dc76c4
Timestamp: 1699961821 Timestamp [UCT]: 2023-11-14 11:37:01 Age [y:d:h:m:s]: 02:009:16:41:56
Block: 891431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526714 RingCT/type: yes/0
Extra: 0111bb8d176cd38d743946e901ea40928711136b70e8db6bca5c149f7264dc76c402110000000675e3f0e9000000000000000000

1 output(s) for total of 0.682840139000 dcy

stealth address amount amount idx
00: ba15e2aba934a95b6535bf9084249bae2e376b8146e5f269bf6db75828d63168 0.682840139000 1347474 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": 891441, "vin": [ { "gen": { "height": 891431 } } ], "vout": [ { "amount": 682840139, "target": { "key": "ba15e2aba934a95b6535bf9084249bae2e376b8146e5f269bf6db75828d63168" } } ], "extra": [ 1, 17, 187, 141, 23, 108, 211, 141, 116, 57, 70, 233, 1, 234, 64, 146, 135, 17, 19, 107, 112, 232, 219, 107, 202, 92, 20, 159, 114, 100, 220, 118, 196, 2, 17, 0, 0, 0, 6, 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