Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4d9b90d21afc9ec13773a2de048f679543c60857fcdffcd47bde23dd02f84e

Tx prefix hash: 32300261f8dfc299cbd795b1fa8baf5a4aa19d8e2cdcbe9db16ac16ccff2dfad
Tx public key: 844bdf2dbdef4f6fd3f3410b79b20fcd00ea1c7218303143d1ca00b4a7435b24
Timestamp: 1583029370 Timestamp [UCT]: 2020-03-01 02:22:50 Age [y:d:h:m:s]: 04:271:08:23:52
Block: 74416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087648 RingCT/type: yes/0
Extra: 01844bdf2dbdef4f6fd3f3410b79b20fcd00ea1c7218303143d1ca00b4a7435b2402110000000ec71d3ff9000000000000000000

1 output(s) for total of 347.880189982000 dcy

stealth address amount amount idx
00: f65942167f7e8217cc4fd82cfea663663a88a7675ef1f5a5756ba96b95b0662a 347.880189982000 137726 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": 74426, "vin": [ { "gen": { "height": 74416 } } ], "vout": [ { "amount": 347880189982, "target": { "key": "f65942167f7e8217cc4fd82cfea663663a88a7675ef1f5a5756ba96b95b0662a" } } ], "extra": [ 1, 132, 75, 223, 45, 189, 239, 79, 111, 211, 243, 65, 11, 121, 178, 15, 205, 0, 234, 28, 114, 24, 48, 49, 67, 209, 202, 0, 180, 167, 67, 91, 36, 2, 17, 0, 0, 0, 14, 199, 29, 63, 249, 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