Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47280d7b89d6745577df05473a1bd0d56e1b82d1d20104d45548a2f00a859e14

Tx prefix hash: 5aeec5f26aea2ca1b2df638ed1593745d32dfde96efeaeb15d434349076d65f0
Tx public key: 29da456e7cf1a6cc28b833ad9be9b8e57c3fc981c17ff371b9e2a1febb128250
Timestamp: 1744945334 Timestamp [UCT]: 2025-04-18 03:02:14 Age [y:d:h:m:s]: 00:213:11:42:24
Block: 1263852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150306 RingCT/type: yes/0
Extra: 0129da456e7cf1a6cc28b833ad9be9b8e57c3fc981c17ff371b9e2a1febb1282500211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1894ad98013a0e063c9d5269c6d2c0c9545b8691c82986309cd44b50d62e7018 0.600000000000 1751045 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": 1263862, "vin": [ { "gen": { "height": 1263852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1894ad98013a0e063c9d5269c6d2c0c9545b8691c82986309cd44b50d62e7018" } } ], "extra": [ 1, 41, 218, 69, 110, 124, 241, 166, 204, 40, 184, 51, 173, 155, 233, 184, 229, 124, 63, 201, 129, 193, 127, 243, 113, 185, 226, 161, 254, 187, 18, 130, 80, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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