Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338663d9b943ed39398af1170eae2fae1549da151b6160e6b5d0cef014387587

Tx prefix hash: 129cc4c6b8395ba2c42407d84109ee9aa6679d02d422b0827eac3fe22567440e
Tx public key: a1786cefdf6ae34969e0bcff347d4af213f82216fa3a5ca62428b4e25eaf2a26
Timestamp: 1716690994 Timestamp [UCT]: 2024-05-26 02:36:34 Age [y:d:h:m:s]: 00:341:08:51:35
Block: 1030127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243996 RingCT/type: yes/0
Extra: 01a1786cefdf6ae34969e0bcff347d4af213f82216fa3a5ca62428b4e25eaf2a260211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d61626804bc8775d8b75e1f905eba4833417f0899edafab0c7b3d03a55f7fba6 0.600000000000 1498380 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": 1030137, "vin": [ { "gen": { "height": 1030127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d61626804bc8775d8b75e1f905eba4833417f0899edafab0c7b3d03a55f7fba6" } } ], "extra": [ 1, 161, 120, 108, 239, 223, 106, 227, 73, 105, 224, 188, 255, 52, 125, 74, 242, 19, 248, 34, 22, 250, 58, 92, 166, 36, 40, 180, 226, 94, 175, 42, 38, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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