Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: accf424f84c5cee1153c694cce43696d2e5f9e05c096f078701e19c32dfeeee3

Tx prefix hash: 6e551852e399148fd2bffad57163e9cc297e6d7b4dc6b3146b0e19a79e78582f
Tx public key: e2a849dc386f80f4dbf3b5f0b7701e07c811be5c75302c3798a9f14dd3c5857d
Timestamp: 1698638609 Timestamp [UCT]: 2023-10-30 04:03:29 Age [y:d:h:m:s]: 01:170:00:02:52
Block: 880670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382498 RingCT/type: yes/0
Extra: 01e2a849dc386f80f4dbf3b5f0b7701e07c811be5c75302c3798a9f14dd3c5857d02110000000179bda3be000000000000000000

1 output(s) for total of 0.741267088000 dcy

stealth address amount amount idx
00: 010a193e2b5a0ce3dce0dd667ce931881b20e9ada5c6fc6595d5b0ffd6783319 0.741267088000 1336234 of 0

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": 880680, "vin": [ { "gen": { "height": 880670 } } ], "vout": [ { "amount": 741267088, "target": { "key": "010a193e2b5a0ce3dce0dd667ce931881b20e9ada5c6fc6595d5b0ffd6783319" } } ], "extra": [ 1, 226, 168, 73, 220, 56, 111, 128, 244, 219, 243, 181, 240, 183, 112, 30, 7, 200, 17, 190, 92, 117, 48, 44, 55, 152, 169, 241, 77, 211, 197, 133, 125, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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