Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5919a906284ee2555a52d38ba05a5a4576a0f103bcd1d1fa357f65636290823

Tx prefix hash: 9c7ddba704f726e85b6b113bc5fa45d7d3cc4776b990b1fc8f9578d3671dbff6
Tx public key: 0dabc2b5e94e54521b95a197e1b897082f652598fb9aed2cdf87a5bab3562272
Timestamp: 1746450343 Timestamp [UCT]: 2025-05-05 13:05:43 Age [y:d:h:m:s]: 00:200:11:16:17
Block: 1276318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140987 RingCT/type: yes/0
Extra: 010dabc2b5e94e54521b95a197e1b897082f652598fb9aed2cdf87a5bab35622720211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6d22cbfde9f9df0b16559cb8fbd00bb9bc9136a0cdab38f176a8d0caa94d305 0.600000000000 1763649 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": 1276328, "vin": [ { "gen": { "height": 1276318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6d22cbfde9f9df0b16559cb8fbd00bb9bc9136a0cdab38f176a8d0caa94d305" } } ], "extra": [ 1, 13, 171, 194, 181, 233, 78, 84, 82, 27, 149, 161, 151, 225, 184, 151, 8, 47, 101, 37, 152, 251, 154, 237, 44, 223, 135, 165, 186, 179, 86, 34, 114, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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