Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d712d5ed13c42f3bc50fd60461645c992e9db90cd89050af5282cdf321fa275b

Tx prefix hash: 266d662ca6a07f4b0e60e4b0ad8b2083ae114cd4387c276b5876579bdca2f1d8
Tx public key: 0c8e0468cf72611bc2c870b06bc7e4e3506af42c865e353548993fabc20a280b
Timestamp: 1582056829 Timestamp [UCT]: 2020-02-18 20:13:49 Age [y:d:h:m:s]: 05:260:04:25:39
Block: 67726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336700 RingCT/type: yes/0
Extra: 010c8e0468cf72611bc2c870b06bc7e4e3506af42c865e353548993fabc20a280b02110000000ed81c26c0000000000000000000

1 output(s) for total of 366.097239878000 dcy

stealth address amount amount idx
00: 383872a0226bc8ceefb536dad5b7342622b8d0812b9e9f3f14e3923d0bef933e 366.097239878000 124735 of 0

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": 67736, "vin": [ { "gen": { "height": 67726 } } ], "vout": [ { "amount": 366097239878, "target": { "key": "383872a0226bc8ceefb536dad5b7342622b8d0812b9e9f3f14e3923d0bef933e" } } ], "extra": [ 1, 12, 142, 4, 104, 207, 114, 97, 27, 194, 200, 112, 176, 107, 199, 228, 227, 80, 106, 244, 44, 134, 94, 53, 53, 72, 153, 63, 171, 194, 10, 40, 11, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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