Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d85139163c03debd8fc2a2faa3f066e387f4df9514c53fc9a88a7d561c27b3

Tx prefix hash: 9bd3244db673998130ad4728d62745905506c4fd72c6e42729f985c0730fdd27
Tx public key: 96d2198fe90fb2fc2bfc10e792e7ec15ca8ee0b2cb8423c1a64f23fda3e7f766
Timestamp: 1737276662 Timestamp [UCT]: 2025-01-19 08:51:02 Age [y:d:h:m:s]: 00:151:13:47:16
Block: 1200600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108048 RingCT/type: yes/0
Extra: 0196d2198fe90fb2fc2bfc10e792e7ec15ca8ee0b2cb8423c1a64f23fda3e7f766021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0308ff708942e96d1c0e9c4068df9d31e40b6f4d657024004e4cbbae39bdfdd6 0.600000000000 1687245 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": 1200610, "vin": [ { "gen": { "height": 1200600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0308ff708942e96d1c0e9c4068df9d31e40b6f4d657024004e4cbbae39bdfdd6" } } ], "extra": [ 1, 150, 210, 25, 143, 233, 15, 178, 252, 43, 252, 16, 231, 146, 231, 236, 21, 202, 142, 224, 178, 203, 132, 35, 193, 166, 79, 35, 253, 163, 231, 247, 102, 2, 17, 0, 0, 0, 4, 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