Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7bbfe359c5843cc9a43eb7c879cb19da652c782289b1b7304e304700ae0f072

Tx prefix hash: 860a432265acdc9d7f68b23c14313a4d8c69a51f8be7d3a54f20ecb192e1f16e
Tx public key: 13b8b27ab13f25437d85af395b6d13923bb1c9dd9459155445446dd1bf74e913
Timestamp: 1694548414 Timestamp [UCT]: 2023-09-12 19:53:34 Age [y:d:h:m:s]: 01:128:00:35:46
Block: 846729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352822 RingCT/type: yes/0
Extra: 0113b8b27ab13f25437d85af395b6d13923bb1c9dd9459155445446dd1bf74e91302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.960362936000 dcy

stealth address amount amount idx
00: 677735be1e171559ee6a62a6c3963b08833b554dcb00c2d880aad1f90515f6ef 0.960362936000 1300209 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": 846739, "vin": [ { "gen": { "height": 846729 } } ], "vout": [ { "amount": 960362936, "target": { "key": "677735be1e171559ee6a62a6c3963b08833b554dcb00c2d880aad1f90515f6ef" } } ], "extra": [ 1, 19, 184, 178, 122, 177, 63, 37, 67, 125, 133, 175, 57, 91, 109, 19, 146, 59, 177, 201, 221, 148, 89, 21, 84, 69, 68, 109, 209, 191, 116, 233, 19, 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