Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a66837d951cf806d3309694c853f9111f014a19c4d0a29f0015dd2c1f8675a

Tx prefix hash: 19889eb27b7c26fdc8cf61671d9d3a4926edb97bd301907d17e1a41ed042ce42
Tx public key: 12173d41209225651f7523982a022ff3cc9cbfdb40ca82e55bee52b1ce7a3edd
Timestamp: 1580788910 Timestamp [UCT]: 2020-02-04 04:01:50 Age [y:d:h:m:s]: 04:296:18:33:37
Block: 58212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103492 RingCT/type: yes/0
Extra: 0112173d41209225651f7523982a022ff3cc9cbfdb40ca82e55bee52b1ce7a3edd02110000000217786bcf000000000000000000

1 output(s) for total of 393.659104315000 dcy

stealth address amount amount idx
00: 329594de5107f76b167c3f0a78eecdf425783fb74ff24946314e5c4357f90ee2 393.659104315000 107600 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": 58222, "vin": [ { "gen": { "height": 58212 } } ], "vout": [ { "amount": 393659104315, "target": { "key": "329594de5107f76b167c3f0a78eecdf425783fb74ff24946314e5c4357f90ee2" } } ], "extra": [ 1, 18, 23, 61, 65, 32, 146, 37, 101, 31, 117, 35, 152, 42, 2, 47, 243, 204, 156, 191, 219, 64, 202, 130, 229, 91, 238, 82, 177, 206, 122, 62, 221, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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