Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db753585f93b8219b7108a37a9690170e2c1b3ef32f7bfa74eb5d8bea37dd19f

Tx prefix hash: 592e7ffaecc138888aa76e694c2618218dcdf6518f99ce514661dd2090052c3c
Tx public key: ed8e71dfb9542516adecd76444f2bc8fb4246fedb30b038314fda93fca2bece1
Timestamp: 1588514676 Timestamp [UCT]: 2020-05-03 14:04:36 Age [y:d:h:m:s]: 04:281:14:15:27
Block: 98024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116520 RingCT/type: yes/0
Extra: 01ed8e71dfb9542516adecd76444f2bc8fb4246fedb30b038314fda93fca2bece10211000002d537fb5df4000000000000000000

1 output(s) for total of 290.540420736000 dcy

stealth address amount amount idx
00: 00ed1c752019f21b9c512de9c4fdb87b81201e209f6e195521b0aa4c1c09b02a 290.540420736000 173371 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": 98034, "vin": [ { "gen": { "height": 98024 } } ], "vout": [ { "amount": 290540420736, "target": { "key": "00ed1c752019f21b9c512de9c4fdb87b81201e209f6e195521b0aa4c1c09b02a" } } ], "extra": [ 1, 237, 142, 113, 223, 185, 84, 37, 22, 173, 236, 215, 100, 68, 242, 188, 143, 180, 36, 111, 237, 179, 11, 3, 131, 20, 253, 169, 63, 202, 43, 236, 225, 2, 17, 0, 0, 2, 213, 55, 251, 93, 244, 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