Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca1dfe8e243a503f3e1a3e0eb223745f9369501ff7c0e2849b1b11bdeb036e89

Tx prefix hash: 16c34e11342d2f46584f32c6f7b323184a9074b1f5e3ced023035d1bb7b0c7bd
Tx public key: 7a1e8040b81e7ca43d6f9c652365751b6c612d98f38545a5774deb0d9156bca1
Timestamp: 1577164806 Timestamp [UCT]: 2019-12-24 05:20:06 Age [y:d:h:m:s]: 05:047:20:58:10
Block: 30389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184096 RingCT/type: yes/0
Extra: 017a1e8040b81e7ca43d6f9c652365751b6c612d98f38545a5774deb0d9156bca102110000000f4fb58672000000000000000000

1 output(s) for total of 486.767695763000 dcy

stealth address amount amount idx
00: e22d8df2f282be890c4d813d04feff235344b0b4cceca48c32ae430ab39f4e94 486.767695763000 50181 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": 30399, "vin": [ { "gen": { "height": 30389 } } ], "vout": [ { "amount": 486767695763, "target": { "key": "e22d8df2f282be890c4d813d04feff235344b0b4cceca48c32ae430ab39f4e94" } } ], "extra": [ 1, 122, 30, 128, 64, 184, 30, 124, 164, 61, 111, 156, 101, 35, 101, 117, 27, 108, 97, 45, 152, 243, 133, 69, 165, 119, 77, 235, 13, 145, 86, 188, 161, 2, 17, 0, 0, 0, 15, 79, 181, 134, 114, 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