Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06993f8a9febe0c1474d969531abc5ea6391a065312e7ca340bd3ddd594ccc65

Tx prefix hash: 0704df36ff251356bc8a63118e7d5e60e7d26fb6b292595cd460249fdaa5560d
Tx public key: 4314390c1d01ad95b534f3e338a66f11fb517706af19beadc25efe0a4128252a
Timestamp: 1704596265 Timestamp [UCT]: 2024-01-07 02:57:45 Age [y:d:h:m:s]: 01:306:09:59:13
Block: 929824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477838 RingCT/type: yes/0
Extra: 014314390c1d01ad95b534f3e338a66f11fb517706af19beadc25efe0a4128252a02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d73e009b3719f0e5e0fc81334864f96030ce54546a5a04dc2fbb6e5e1bb106a 0.600000000000 1387700 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": 929834, "vin": [ { "gen": { "height": 929824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d73e009b3719f0e5e0fc81334864f96030ce54546a5a04dc2fbb6e5e1bb106a" } } ], "extra": [ 1, 67, 20, 57, 12, 29, 1, 173, 149, 181, 52, 243, 227, 56, 166, 111, 17, 251, 81, 119, 6, 175, 25, 190, 173, 194, 94, 254, 10, 65, 40, 37, 42, 2, 17, 0, 0, 0, 7, 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