Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d93cac9fa784880cea2b82d1c4204b0af557d0a06f52a17d20e909dfb37cbc

Tx prefix hash: b6d3378e87006e1a740a00f8b917eaee478910c894a49f0697409ac26ac19fb0
Tx public key: 37bd55f1898d6de957e08dd9687ddc4d176b505095f4427c5cef387adfd5201e
Timestamp: 1724166186 Timestamp [UCT]: 2024-08-20 15:03:06 Age [y:d:h:m:s]: 00:277:03:06:32
Block: 1092103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197960 RingCT/type: yes/0
Extra: 0137bd55f1898d6de957e08dd9687ddc4d176b505095f4427c5cef387adfd5201e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844806ae2cee4c4a6d60869b5d90dae888e222533684fc5f70e9a5c9ad2d7d43 0.600000000000 1566784 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": 1092113, "vin": [ { "gen": { "height": 1092103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844806ae2cee4c4a6d60869b5d90dae888e222533684fc5f70e9a5c9ad2d7d43" } } ], "extra": [ 1, 55, 189, 85, 241, 137, 141, 109, 233, 87, 224, 141, 217, 104, 125, 220, 77, 23, 107, 80, 80, 149, 244, 66, 124, 92, 239, 56, 122, 223, 213, 32, 30, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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