Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63ffc943483f7e4e5a08766c46b4a6b08e72abb316961445eb0e5b3729fc2d0

Tx prefix hash: 66bd7b874d6fe4add2dccad4775b29f963d687f5ddf7473e7405d0df3118ceb6
Tx public key: 1ba6b6fda955d3e70dfdacbbe1b0e1a6406e445541eee19e89641bd4888a1771
Timestamp: 1736993318 Timestamp [UCT]: 2025-01-16 02:08:38 Age [y:d:h:m:s]: 00:152:15:30:59
Block: 1198287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108818 RingCT/type: yes/0
Extra: 011ba6b6fda955d3e70dfdacbbe1b0e1a6406e445541eee19e89641bd4888a1771021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b2dc56498da4110ba688cdc101898cb3c203898f257f266044e175a03c1b5d9 0.600000000000 1684910 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": 1198297, "vin": [ { "gen": { "height": 1198287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b2dc56498da4110ba688cdc101898cb3c203898f257f266044e175a03c1b5d9" } } ], "extra": [ 1, 27, 166, 182, 253, 169, 85, 211, 231, 13, 253, 172, 187, 225, 176, 225, 166, 64, 110, 68, 85, 65, 238, 225, 158, 137, 100, 27, 212, 136, 138, 23, 113, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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