Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecad6489dd219441f0208b680d2dbbf6219e01ddd003907b957cca34234ae686

Tx prefix hash: 9cafddc148d7a439ee93a2131074a89c7431fc24a9cd6a23c6ffa676f8b6d689
Tx public key: 0e00c1e64b4a7adc35a046dc736cf1b20b8fcc139d3e1048065ff37714fc91e5
Timestamp: 1580788037 Timestamp [UCT]: 2020-02-04 03:47:17 Age [y:d:h:m:s]: 05:029:20:57:43
Block: 58178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173418 RingCT/type: yes/0
Extra: 010e00c1e64b4a7adc35a046dc736cf1b20b8fcc139d3e1048065ff37714fc91e502110000000249b77a3d000000000000000000

1 output(s) for total of 393.761232891000 dcy

stealth address amount amount idx
00: 1b620bfa9b53d2074c283184840b5ba82a1f84f6bae5b18bef517a8762ffa950 393.761232891000 107548 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": 58188, "vin": [ { "gen": { "height": 58178 } } ], "vout": [ { "amount": 393761232891, "target": { "key": "1b620bfa9b53d2074c283184840b5ba82a1f84f6bae5b18bef517a8762ffa950" } } ], "extra": [ 1, 14, 0, 193, 230, 75, 74, 122, 220, 53, 160, 70, 220, 115, 108, 241, 178, 11, 143, 204, 19, 157, 62, 16, 72, 6, 95, 243, 119, 20, 252, 145, 229, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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