Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344f528a26fff7fe0b379e7f03394bccf2dcafd5d2ecc53f81b66c4c904363c8

Tx prefix hash: 40fa5ac2dba1203398d3318ee54ec1ecb8445e0da6fa0585fc1bc00493793787
Tx public key: 55450f9392a46ed24d9456313e1d3c0fbe2a8c7f66a88561b3ee0d4dc1f63d7d
Timestamp: 1736490755 Timestamp [UCT]: 2025-01-10 06:32:35 Age [y:d:h:m:s]: 00:072:15:11:31
Block: 1194137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51674 RingCT/type: yes/0
Extra: 0155450f9392a46ed24d9456313e1d3c0fbe2a8c7f66a88561b3ee0d4dc1f63d7d02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864192bf9b5ccc2b4fd7596004617a8680fa1b59e0ae34a12df30a394a9aee38 0.600000000000 1680704 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": 1194147, "vin": [ { "gen": { "height": 1194137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864192bf9b5ccc2b4fd7596004617a8680fa1b59e0ae34a12df30a394a9aee38" } } ], "extra": [ 1, 85, 69, 15, 147, 146, 164, 110, 210, 77, 148, 86, 49, 62, 29, 60, 15, 190, 42, 140, 127, 102, 168, 133, 97, 179, 238, 13, 77, 193, 246, 61, 125, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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