Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5117f93667e305a8df3b4290d266b8989f3ceb6feb1127972199c47554ab5fbc

Tx prefix hash: f9af097b3854585c32be39644602d28970ef7a465ff09e3ac80b63c2dc112008
Tx public key: e0f3d9eb7c7db1b319bb8791266ba28087013d70ed6340fecc943fe2c1f9a0c9
Timestamp: 1719738779 Timestamp [UCT]: 2024-06-30 09:12:59 Age [y:d:h:m:s]: 00:352:17:26:18
Block: 1055390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251967 RingCT/type: yes/0
Extra: 01e0f3d9eb7c7db1b319bb8791266ba28087013d70ed6340fecc943fe2c1f9a0c902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7d81cee73ec93b657dcbc16e1e1416ee66ea4f3e8373d1baecb1faf56f0df0 0.600000000000 1525789 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": 1055400, "vin": [ { "gen": { "height": 1055390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7d81cee73ec93b657dcbc16e1e1416ee66ea4f3e8373d1baecb1faf56f0df0" } } ], "extra": [ 1, 224, 243, 217, 235, 124, 125, 177, 179, 25, 187, 135, 145, 38, 107, 162, 128, 135, 1, 61, 112, 237, 99, 64, 254, 204, 148, 63, 226, 193, 249, 160, 201, 2, 17, 0, 0, 0, 4, 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