Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5069b6fafb97a4bd2cf72969a41dec1a81f4b8dbde5feda731b50b6642e8f73

Tx prefix hash: 28d4f0195a47a0bdd850442b7d2aea7aec8ce3a11a39bf2618b706c6a4b81ad9
Tx public key: df2a3356732bbd77ce12a026ca60880530ba51051fd674e81d36c5fd0f492272
Timestamp: 1657011688 Timestamp [UCT]: 2022-07-05 09:01:28 Age [y:d:h:m:s]: 02:125:10:53:42
Block: 537055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610969 RingCT/type: yes/0
Extra: 01df2a3356732bbd77ce12a026ca60880530ba51051fd674e81d36c5fd0f4922720211000000025eb576c5000000000000000000

1 output(s) for total of 10.197976201000 dcy

stealth address amount amount idx
00: 60c9416349f90e4770ffdc10d250d5607f72a559204f3e0f84384a9203bb0223 10.197976201000 966900 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": 537065, "vin": [ { "gen": { "height": 537055 } } ], "vout": [ { "amount": 10197976201, "target": { "key": "60c9416349f90e4770ffdc10d250d5607f72a559204f3e0f84384a9203bb0223" } } ], "extra": [ 1, 223, 42, 51, 86, 115, 43, 189, 119, 206, 18, 160, 38, 202, 96, 136, 5, 48, 186, 81, 5, 31, 214, 116, 232, 29, 54, 197, 253, 15, 73, 34, 114, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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