Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c836bb6018d2149a99834a16033270a7d8a5592dd6f342d5ff75055e437efc8

Tx prefix hash: 2259a51c2a5431a4d4d7dfbebfa1feff35de3ec57431c76675a4655e073b1bb9
Tx public key: 0267d2da195810e93b0d028e0eb7f936d07c5c68fdb90c9a3d5f6965f12c0771
Timestamp: 1702640973 Timestamp [UCT]: 2023-12-15 11:49:33 Age [y:d:h:m:s]: 01:035:17:09:02
Block: 913636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286847 RingCT/type: yes/0
Extra: 010267d2da195810e93b0d028e0eb7f936d07c5c68fdb90c9a3d5f6965f12c077102110000001633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3058225573e4f8f94aab2d97e6b44e4e5adfdb88d0db53656a460feb7fab650d 0.600000000000 1370912 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": 913646, "vin": [ { "gen": { "height": 913636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3058225573e4f8f94aab2d97e6b44e4e5adfdb88d0db53656a460feb7fab650d" } } ], "extra": [ 1, 2, 103, 210, 218, 25, 88, 16, 233, 59, 13, 2, 142, 14, 183, 249, 54, 208, 124, 92, 104, 253, 185, 12, 154, 61, 95, 105, 101, 241, 44, 7, 113, 2, 17, 0, 0, 0, 22, 51, 175, 153, 244, 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