Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4566a3519cf4613860bdf3bfa0a4ee61cf77a0c661f06fb3c607202471342cc3

Tx prefix hash: 90087a8b00fa74a9db91ae77c104989b4033446eb2ab4fb900640aeebef146f0
Tx public key: d99cf8bdf7f5c99a107feedf9ca414688dc6df5b2ae82e3e16e8e500579c049e
Timestamp: 1733590857 Timestamp [UCT]: 2024-12-07 17:00:57 Age [y:d:h:m:s]: 00:190:13:14:46
Block: 1170132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135923 RingCT/type: yes/0
Extra: 01d99cf8bdf7f5c99a107feedf9ca414688dc6df5b2ae82e3e16e8e500579c049e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7a1b3d561329d537d65eb47d1862264a041630d242ddb3e54e60c52a11a96e6 0.600000000000 1655861 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": 1170142, "vin": [ { "gen": { "height": 1170132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7a1b3d561329d537d65eb47d1862264a041630d242ddb3e54e60c52a11a96e6" } } ], "extra": [ 1, 217, 156, 248, 189, 247, 245, 201, 154, 16, 127, 238, 223, 156, 164, 20, 104, 141, 198, 223, 91, 42, 232, 46, 62, 22, 232, 229, 0, 87, 156, 4, 158, 2, 17, 0, 0, 0, 7, 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