Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58cc647612c2028d1493cf4058dca7870b222613fc2c755c736868e7c173196e

Tx prefix hash: b489cb7c42609a48902325d6b2629283f2876909b5b358f4ba7d14b684827df7
Tx public key: 1d92424525794b94b1a910f087d020fb6364a17e8c09913427757735cf892f2b
Timestamp: 1584921905 Timestamp [UCT]: 2020-03-23 00:05:05 Age [y:d:h:m:s]: 04:254:12:25:17
Block: 86860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078842 RingCT/type: yes/0
Extra: 011d92424525794b94b1a910f087d020fb6364a17e8c09913427757735cf892f2b021100000009d81c26c0000000000000000000

1 output(s) for total of 316.371637665000 dcy

stealth address amount amount idx
00: 3fd03c606db4d30dbf1aa442df70415168001a6f32af7aa527c0ff05a749f728 316.371637665000 156686 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": 86870, "vin": [ { "gen": { "height": 86860 } } ], "vout": [ { "amount": 316371637665, "target": { "key": "3fd03c606db4d30dbf1aa442df70415168001a6f32af7aa527c0ff05a749f728" } } ], "extra": [ 1, 29, 146, 66, 69, 37, 121, 75, 148, 177, 169, 16, 240, 135, 208, 32, 251, 99, 100, 161, 126, 140, 9, 145, 52, 39, 117, 119, 53, 207, 137, 47, 43, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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