Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862df3aca27bfcdd8e5a5e9da16c440fa3c49e77af4c99e3fa2d808a45389a54

Tx prefix hash: a7c60c4828e15f5f105e6794519c0e25195a4cd61487262e64442995acdbd7df
Tx public key: 82cbe4a9cb8d9a49e0e9276b500856ceacd9afa980b462bc4ce70f3dcc0f7eb2
Timestamp: 1714601768 Timestamp [UCT]: 2024-05-01 22:16:08 Age [y:d:h:m:s]: 00:142:15:28:23
Block: 1012805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102175 RingCT/type: yes/0
Extra: 0182cbe4a9cb8d9a49e0e9276b500856ceacd9afa980b462bc4ce70f3dcc0f7eb202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b0d649513f895ba678a3a2545e41f03fbb7b4bd81c9791e3ca0461bc01d5fa5 0.600000000000 1475437 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": 1012815, "vin": [ { "gen": { "height": 1012805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b0d649513f895ba678a3a2545e41f03fbb7b4bd81c9791e3ca0461bc01d5fa5" } } ], "extra": [ 1, 130, 203, 228, 169, 203, 141, 154, 73, 224, 233, 39, 107, 80, 8, 86, 206, 172, 217, 175, 169, 128, 180, 98, 188, 76, 231, 15, 61, 204, 15, 126, 178, 2, 17, 0, 0, 0, 3, 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