Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b8be1bbe4ca7856d7229eca081ed9206d865fcb1878a0c95e8be360e551814

Tx prefix hash: fc7281576e191e7287630991db4aaf32b288e791da9cc727d9e3476563a1392a
Tx public key: a715c22a7a937a5d7f2912285b89a6c994df7d12c31221bf69035b3e8748184b
Timestamp: 1713657592 Timestamp [UCT]: 2024-04-20 23:59:52 Age [y:d:h:m:s]: 00:201:01:49:08
Block: 1004962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143952 RingCT/type: yes/0
Extra: 01a715c22a7a937a5d7f2912285b89a6c994df7d12c31221bf69035b3e8748184b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d8df9e6c0165a2604a71679194992fa42be020663dcc22dae1786f1173b981c 0.600000000000 1465536 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": 1004972, "vin": [ { "gen": { "height": 1004962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d8df9e6c0165a2604a71679194992fa42be020663dcc22dae1786f1173b981c" } } ], "extra": [ 1, 167, 21, 194, 42, 122, 147, 122, 93, 127, 41, 18, 40, 91, 137, 166, 201, 148, 223, 125, 18, 195, 18, 33, 191, 105, 3, 91, 62, 135, 72, 24, 75, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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