Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1c512b533dbb741d9104e3ddb919e65cd6c36d2454c5b47818c0e935fab6e9

Tx prefix hash: cc7704cef7bed63f31e22b2d4796e60f92d0dfc35d01f8e7d20a7634e7ffc971
Tx public key: 2bd819bc44e4e9fab7b0b4251df43e70ab2eb69125907f3d1ed031b8a2c7f572
Timestamp: 1716511128 Timestamp [UCT]: 2024-05-24 00:38:48 Age [y:d:h:m:s]: 00:333:09:23:31
Block: 1028634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238290 RingCT/type: yes/0
Extra: 012bd819bc44e4e9fab7b0b4251df43e70ab2eb69125907f3d1ed031b8a2c7f57202110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff7630feb1414a376b0414cf7525757558ecd5b774ed40e21cbf537170f3b658 0.600000000000 1496629 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": 1028644, "vin": [ { "gen": { "height": 1028634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff7630feb1414a376b0414cf7525757558ecd5b774ed40e21cbf537170f3b658" } } ], "extra": [ 1, 43, 216, 25, 188, 68, 228, 233, 250, 183, 176, 180, 37, 29, 244, 62, 112, 171, 46, 182, 145, 37, 144, 127, 61, 30, 208, 49, 184, 162, 199, 245, 114, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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