Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e66a299c3505e9cb50dccabb3c800c3b2e4f20a20a295c285c7b010c4c022e9

Tx prefix hash: f189504d9b34fac0fef3cdb43b32af46d7cd8bf59b9034c44a1161d307708884
Tx public key: c40baa5d7a1efc189a66cd54278f0528ca23c1b7a1fce2f1ab1633b8857b1303
Timestamp: 1580622680 Timestamp [UCT]: 2020-02-02 05:51:20 Age [y:d:h:m:s]: 04:278:06:57:40
Block: 56951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090138 RingCT/type: yes/0
Extra: 01c40baa5d7a1efc189a66cd54278f0528ca23c1b7a1fce2f1ab1633b8857b13030211000000012264afe6000000000000000000

1 output(s) for total of 397.464658421000 dcy

stealth address amount amount idx
00: ea1a0d32b1abdcba68696e95431efbd77d451fa0a7f5d894c34e79d71b8d844d 397.464658421000 104998 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": 56961, "vin": [ { "gen": { "height": 56951 } } ], "vout": [ { "amount": 397464658421, "target": { "key": "ea1a0d32b1abdcba68696e95431efbd77d451fa0a7f5d894c34e79d71b8d844d" } } ], "extra": [ 1, 196, 11, 170, 93, 122, 30, 252, 24, 154, 102, 205, 84, 39, 143, 5, 40, 202, 35, 193, 183, 161, 252, 226, 241, 171, 22, 51, 184, 133, 123, 19, 3, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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