Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc5f89af7bed24c40837f1cdd4b8be46e4d2a3f9fd7493e3f7a279b05aca6cc

Tx prefix hash: f7f45703d1183ea690f6db1933a34fcf992b06cfeda670847f5849c1a7b9c1ba
Tx public key: 45e94aa5d3da54da82b4ad8f654b3a456d12f9b0b8607074af072bc3eddf34a0
Timestamp: 1582237338 Timestamp [UCT]: 2020-02-20 22:22:18 Age [y:d:h:m:s]: 05:258:09:43:54
Block: 68983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1335673 RingCT/type: yes/0
Extra: 0145e94aa5d3da54da82b4ad8f654b3a456d12f9b0b8607074af072bc3eddf34a00211000000044ac5aa02000000000000000000

1 output(s) for total of 362.603081029000 dcy

stealth address amount amount idx
00: 0b52df163e5f412a8aab573b38adcfcb49dfa64a579b22b26467cdf8ba8b85e2 362.603081029000 127246 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": 68993, "vin": [ { "gen": { "height": 68983 } } ], "vout": [ { "amount": 362603081029, "target": { "key": "0b52df163e5f412a8aab573b38adcfcb49dfa64a579b22b26467cdf8ba8b85e2" } } ], "extra": [ 1, 69, 233, 74, 165, 211, 218, 84, 218, 130, 180, 173, 143, 101, 75, 58, 69, 109, 18, 249, 176, 184, 96, 112, 116, 175, 7, 43, 195, 237, 223, 52, 160, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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