Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9cdd3ac8ee939a195326d12eb0106f4962650b920fb08ad2c0389f1575bd89e

Tx prefix hash: a7a8b86615fea8f2422299f7712cd7de62c78d3fb9f587c68bf0ec91154759fb
Tx public key: 758262d5453aae6695a1f299ddb73806e97fbfb5b58aa7dfd80e5c98a926d9eb
Timestamp: 1582063054 Timestamp [UCT]: 2020-02-18 21:57:34 Age [y:d:h:m:s]: 05:015:02:10:52
Block: 67749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163837 RingCT/type: yes/0
Extra: 01758262d5453aae6695a1f299ddb73806e97fbfb5b58aa7dfd80e5c98a926d9eb0211000000154ac5aa02000000000000000000

1 output(s) for total of 366.033003962000 dcy

stealth address amount amount idx
00: 7a8b4492e880bf76e314107b15cfd3236cb61a12b4e1ae7eba84dc28c7502140 366.033003962000 124788 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": 67759, "vin": [ { "gen": { "height": 67749 } } ], "vout": [ { "amount": 366033003962, "target": { "key": "7a8b4492e880bf76e314107b15cfd3236cb61a12b4e1ae7eba84dc28c7502140" } } ], "extra": [ 1, 117, 130, 98, 213, 69, 58, 174, 102, 149, 161, 242, 153, 221, 183, 56, 6, 233, 127, 191, 181, 181, 138, 167, 223, 216, 14, 92, 152, 169, 38, 217, 235, 2, 17, 0, 0, 0, 21, 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