Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab70670d6559f3e98d275e41f22f4e4120a8e942009ed3b8a8392cdb155eb7f5

Tx prefix hash: 66f16363a517027f1381c752e8ca8047bff63252efe928753d2b8f0bb2f534cd
Tx public key: 8d6d9cbcf5155eacb773b3a7325a57cff4d1f887f025de56169536db9b1edcea
Timestamp: 1716824493 Timestamp [UCT]: 2024-05-27 15:41:33 Age [y:d:h:m:s]: 00:227:17:01:29
Block: 1031245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162950 RingCT/type: yes/0
Extra: 018d6d9cbcf5155eacb773b3a7325a57cff4d1f887f025de56169536db9b1edcea0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a262ff533f4adb5588c32671020ee6f2aaace0aa43c5f693b321295fbc8e7240 0.600000000000 1499644 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": 1031255, "vin": [ { "gen": { "height": 1031245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a262ff533f4adb5588c32671020ee6f2aaace0aa43c5f693b321295fbc8e7240" } } ], "extra": [ 1, 141, 109, 156, 188, 245, 21, 94, 172, 183, 115, 179, 167, 50, 90, 87, 207, 244, 209, 248, 135, 240, 37, 222, 86, 22, 149, 54, 219, 155, 30, 220, 234, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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