Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fafe774cce00948697c026c01f44140b9c1672ce95838f25fa27effd807041b4

Tx prefix hash: b2876da6d3b0286f2835c133bc83d80096b52ee409f828cd3b602ddc6458232c
Tx public key: ff4bd7d3f5a51da4ac0a2db2ed5b8a4363dc354d9444f518884934228f6218f9
Timestamp: 1584524082 Timestamp [UCT]: 2020-03-18 09:34:42 Age [y:d:h:m:s]: 05:029:20:55:26
Block: 84860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177669 RingCT/type: yes/0
Extra: 01ff4bd7d3f5a51da4ac0a2db2ed5b8a4363dc354d9444f518884934228f6218f90211000000014943cd9f000000000000000000

1 output(s) for total of 321.239903000000 dcy

stealth address amount amount idx
00: 571f8ccdeff76f5a6822f7989e18b41b5c5a1cf34c7929545a87caabfe13f437 321.239903000000 153610 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": 84870, "vin": [ { "gen": { "height": 84860 } } ], "vout": [ { "amount": 321239903000, "target": { "key": "571f8ccdeff76f5a6822f7989e18b41b5c5a1cf34c7929545a87caabfe13f437" } } ], "extra": [ 1, 255, 75, 215, 211, 245, 165, 29, 164, 172, 10, 45, 178, 237, 91, 138, 67, 99, 220, 53, 77, 148, 68, 245, 24, 136, 73, 52, 34, 143, 98, 24, 249, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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