Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 216c91a6febfa53decfe1a062ec6098a2d3851720dbad86abbc28da1441a8f6e

Tx prefix hash: bb2d71c600ada00a2b1e8fd0272221c7cecf6f8f996a6e64e1bc7440e9f8c897
Tx public key: 7900cee6a1a045c9e531278488b7103f7dc92cc5ba1034f2882805597c381d7d
Timestamp: 1719226892 Timestamp [UCT]: 2024-06-24 11:01:32 Age [y:d:h:m:s]: 01:136:15:18:09
Block: 1051137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356208 RingCT/type: yes/0
Extra: 017900cee6a1a045c9e531278488b7103f7dc92cc5ba1034f2882805597c381d7d02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98b62f6b00a05706763dae283dba58119bbe343d2d1f8ad7a5846e1cea9e58c2 0.600000000000 1521392 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": 1051147, "vin": [ { "gen": { "height": 1051137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98b62f6b00a05706763dae283dba58119bbe343d2d1f8ad7a5846e1cea9e58c2" } } ], "extra": [ 1, 121, 0, 206, 230, 161, 160, 69, 201, 229, 49, 39, 132, 136, 183, 16, 63, 125, 201, 44, 197, 186, 16, 52, 242, 136, 40, 5, 89, 124, 56, 29, 125, 2, 17, 0, 0, 0, 8, 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