Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5898f1424f99738f4f6d53eae62bb072d85e211bc4038160456bf92d29ec32d

Tx prefix hash: 30c7c4f6893e7aa3c25fbacb30160ba16db22868e3851f69f91f9dcdb366fab3
Tx public key: b3eb68efd90b39720e59fca9bd65c4b6e426264ab3f8e6685a480f0f12950a7d
Timestamp: 1712755822 Timestamp [UCT]: 2024-04-10 13:30:22 Age [y:d:h:m:s]: 01:236:11:47:48
Block: 997471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427750 RingCT/type: yes/0
Extra: 01b3eb68efd90b39720e59fca9bd65c4b6e426264ab3f8e6685a480f0f12950a7d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4448a0a38b5d1787c1a9a3c93016ea757fd2fc7b2ecf460f1a2794d9b8e52007 0.600000000000 1457903 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": 997481, "vin": [ { "gen": { "height": 997471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4448a0a38b5d1787c1a9a3c93016ea757fd2fc7b2ecf460f1a2794d9b8e52007" } } ], "extra": [ 1, 179, 235, 104, 239, 217, 11, 57, 114, 14, 89, 252, 169, 189, 101, 196, 182, 228, 38, 38, 74, 179, 248, 230, 104, 90, 72, 15, 15, 18, 149, 10, 125, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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