Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50f335831d217d31f84af028f3e09d7f49b2baf304f48b0fe24f31212a1cd5f

Tx prefix hash: d5eb8fe6c89ecfb8c1b7711c20565265aff13a7843881e20d54229ee5c8b0015
Tx public key: 33d561c9aa52a573f24d531e7aac61705921018c7ca7a9f4d2c0c971e59424f7
Timestamp: 1710370759 Timestamp [UCT]: 2024-03-13 22:59:19 Age [y:d:h:m:s]: 01:062:16:26:33
Block: 977748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305798 RingCT/type: yes/0
Extra: 0133d561c9aa52a573f24d531e7aac61705921018c7ca7a9f4d2c0c971e59424f702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a204653472fa23d700e127785e0405ac8fc0c1495241b879bb44d4ce062fd3b0 0.600000000000 1437753 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": 977758, "vin": [ { "gen": { "height": 977748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a204653472fa23d700e127785e0405ac8fc0c1495241b879bb44d4ce062fd3b0" } } ], "extra": [ 1, 51, 213, 97, 201, 170, 82, 165, 115, 242, 77, 83, 30, 122, 172, 97, 112, 89, 33, 1, 140, 124, 167, 169, 244, 210, 192, 201, 113, 229, 148, 36, 247, 2, 17, 0, 0, 0, 4, 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